docs: document release workflow and version selection#30
Merged
nnemirovsky merged 1 commit intomainfrom Apr 13, 2026
Merged
Conversation
nnemirovsky
force-pushed
the
docs-release-workflow
branch
from
b06e4c9 to
8dd1637
Compare
nnemirovsky
force-pushed
the
docs-release-workflow
branch
from
8dd1637 to
58e4f62
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds release instructions to CLAUDE.md: use
/release-tools:newskill, tag naming (vX.Y.Z), when to pick minor vs hotfix vs major, and how the goreleaser workflow handles existing releases.Closes the gap where I used "Version X.Y.Z" as the release title and created the GitHub release manually instead of letting goreleaser do it.